Automated package information and configuration communication process

ABSTRACT

A system and method for processing project data enables a user to identify an engine model based on specific customer specifications. Package options based on the identified engine model are stored in the system, and a user is able to select desired package options from the stored package options. Selected reports can be generated based on the selected package options. In this manner, product and project information can be communicated upstream to sales and/or the customer, project specific information can be communicated downstream to project execution, the business process can be directed and automated, and historical data on all projects and revisions can be maintained.

BACKGROUND OF THE INVENTION

[0001] The present invention relates to a database structure and methodof processing project data and, more particularly, to an automatedpackage information and configuration communication process forcommunicating product information upstream to a sales department or thelike and a customer, project specific information downstream to projectexecution, direct and automate a business process, and maintainhistorical data on all projects and revisions.

[0002]FIG. 1 is a schematic illustration of a business process flow.Generally, in an inquiry to order (ITO) process, a sales team firstinterfaces with a customer, followed by a request for quote (RFQ) beingsubmitted to the sales support group. Sales support would then break theRFQ into commercial and technical issues, and the technical issues(including a customer specification) would be submitted to the productmanagement group.

[0003] The product management group would then review the customerspecification and create two documents: (1) a production data sheet(PDS) presenting the scope of supply, and (2) a budget that identifiesthe cost to manufacture the defined scope based on the customer request.Both documents have generally been configured using known spreadsheetcomputer programs. These spreadsheets are then submitted to salessupport via an iterative process until the scope of the project is welldefined and accurate. A proposal would then be generated by salessupport and submitted to the customer for review.

[0004] Assuming the company wins the bid, an agreement in principle(AIP) or contract will be signed and submitted along with a sales ordersummary (SOS) document that is also based on the project scope, toproduct management group for final review and the hand-over meeting(HOM) to OTR. The HOM consists of the project team meeting and reviewingthe numerous documents (including the PDS, budget, SOS and an open itemsdocument among others) to verify that the project scope is accurate,attainable and consistent from document to document. A final revision ismade to the documentation, and the resulting information is submitted toproject management for execution.

[0005] Project management then meets directly with the customer to beginaddressing the open items, revising PDS and SOS documents, and releasingthe information to engineering. Engineering would then review theofficial documents and create a features and options document detailingwhat drawings are required to manufacture and assemble the package.

[0006] In addition to the multiple points of data entry, excessivenumbers of documents presenting information based on a single scope ofsupply are required, multiple document translations and hours ofunnecessary work are also required, and there exist no running budget,open item metrics, project metrics, business impact measurements orbudgetary analysis capabilities within the current process.

[0007] Package configuration and information is thus scattered acrossnumerous documents that are often identified as inconsistent, inaccurateand/or out-of-date. Moreover, the multiple documents are time consumingto create and maintain and they do not allow for statistical analysisfacilitating future process improvement.

BRIEF DESCRIPTION OF THE INVENTION

[0008] In an exemplary embodiment of the present invention, a method ofprocessing project data includes (a) receiving customer specifications,(b) identifying an engine model based on the customer specifications,(c) storing package options based on the engine model identified in (b),(d) enabling a user to select the package options from the storedpackage options, and (e) generating selected reports based on thepackage options selected in (d).

[0009] In another exemplary embodiment of the invention, a system forprocessing project data including structure for carrying out the methodof the invention is provided.

[0010] In still another exemplary embodiment of the invention, a systemfor processing project data includes a user interface for receivingcustomer specifications and identifying an engine model based on thecustomer specifications. The processor including a memory storingpackage options that are segregated based on the identified engine modelenables a user to select the package options from the stored packageoptions via the user interface. The processor generates selected reportsbased on the selected package options.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011]FIG. 1 is a business process flow diagram;

[0012]FIG. 2 is a flow diagram of the general process of the presentinvention;

[0013]FIG. 3 is a flow diagram showing the process for revising theconfiguration/project information;

[0014]FIG. 4 is a flow diagram for modifying the drawing list;

[0015]FIG. 5 is a flow diagram for creating/modifying a budgetaryanalysis;

[0016]FIG. 6 is a flow diagram for tool maintenance;

[0017]FIG. 7 is a flow diagram for viewing sales tools;

[0018]FIG. 8 is a screen shot showing a user interface and packageconfiguration;

[0019]FIG. 9 is a screen shot showing project information; and

[0020]FIG. 10 is a flow diagram showing an approval process.

DETAILED DESCRIPTION OF THE INVENTION

[0021] A database configuration in the present invention includes datatables that respectively store varying information for a particularproject. The invention will be described in the context of a particularapplication for exemplary purposes, but the invention is not necessarilymeant to be limited to the described application.

[0022] In the database, an engine table holds all of the differentengines offered via the system to provide in a configuration package. Inthe engine table, an ID field orders the list of engine models on apull-down menu, with the lowest number at the top of the list and withthe remaining models following in ascending order. In an Engine Descfield, the name of each engine model is provided. The names are used fordisplay in the pull-down menu and matched up with the engine key in themodel table to determine which database is to be opened.

[0023] In a model table, all of the models associated with each of theengines are stored. In an EngineKey field, a list of engine types isprovided. Each engine type is listed once for each model to which it isassociated. In a Model Desc field, the names of each model offered foreach engine type are provided. A second pull-down menu will only displaythe values in the model description field that are associated with theengine key field value that the user selects in the first pull-downmenu. A Default field determines which database is initially loaded foreach engine type. The field should also be checked if the engine typeonly has one model description associated with it.

[0024] There is a specific table for each of the engine models. Thistable holds all of the package options for the selected model with anesting structure used to identify the applicable options based for userinput. The table also contains information such as what validation logicapplies to the option, whether the option is mandatory, whether theoption is the default option, the associated key to that option, and ametric score.

[0025] In a package options table, a Text field contains a title of amain heading of a section down to the deepest level of configurationselection choices. A Level field determines the nesting order of theconfiguration choices and formats a corresponding display. A highestchoice or title is given a level of one (1). The program then checks forand indents displays of all configuration choices with a level of two(2) rating. The database does a similar procedure with every new levelencountered. It indents farther with each new level and returns to itsoriginal level of indentation when a configuration selection is reachedwith the level number equivalent to its own. Therefore, for example, alllevel twos are indented the same amount as with level threes and so onwhile remaining underneath their respective section. (See, for example,FIG. 8.) An Option field defines if the user has the ability to selectthe configuration choice. For titles or main sections, the field is leftunselected. If the field is selected, then the user will have theability to select or unselect the choice in the configuration section ofthe program. A Standard field is selected if that configuration choiceis selected by default when the option becomes available throughinteraction. The user, however, maintains the ability to select anotheroption on that same nest level. A MultiSelect field, if selected, for anest level, allows the user to select multiple options in that nestlevel. If unselected, the user must choose one and only one option inthe corresponding nest level. A Key field includes a keyword relating aconfiguration selection to the budget and drawing numbers. A Metricfield includes a score attached to main selection criteria identifyingthe importance of the information. The greater score is reported foritems that have a greater business impact when unknown or changed. Theoverall metric adds up to the scores of all sections that have been leftblank or “to be determined.”

[0026] In a configuration flag table, all potential keys for the packageoptions are contained. The keys tie user selections to budgetary anddrawing information for reporting purposes. In a Keyword field, a listof words that are used to associate the configuration selections withdrawing numbers and budgetary costs is provided.

[0027] A budgetary cost table holds the information necessary to createthe budget. This information includes budget section, line items,description, cost, required keys per line item, and whether or not theline item is part of the base package. A Section field defines whichbudget section the particular line item will fall under. A SectionIDfield identifies the order the line item will be placed inside the majorsection of the budget report. Each line item is given a one letter codeand is displayed in the budget report in alphabetical order. ADescription field contains the name of the budgetary unit used forpricing the different components of the package. A UnitCost fieldincludes the price of each budgetary unit that is displayed and summedin the total cost on the budget report if the user has selected theoption from the configuration section. Fields from Key 1-Key 10 includewords used to specify which line item should be entered into the budgetreport. These words are the same as the key words attached to theconfiguration options. When a configuration has been selected, theassociated keywords are compared to the ones in each key column todetermine what cost line items are applicable to the user definedconfiguration. Up to ten keywords can be used to differentiate thedifferent budgetary cost line items from one another. Only one keywordcan be entered into each of the ten key columns. Multiple flag fieldsdesignated Flag 1-Flag 10 contain logic criteria associated withkeywords in the Key 1-Key 10 columns. If the check box is checked, thenthe keyword in the key column of the same number as the flag must betrue in order to select the particular line item. If the check box isunchecked, then the keyword in the associated column must be false ornot present in the current configuration selections in order to selectthe particular line item.

[0028] A features and options table holds the information necessary tocreate a features and options document. This information includes thesystem, drawing numbers and associated keys per line item. A Sectionfield defines which section of the features and option report thedrawing will fall under. A DwgNumber field contains the drawing number,wherein when the keyword criteria is met, the drawing number in thisfield is inserted under the appropriate section. Similar to thebudgetary cost table, the features and options table contains key fieldsincluding Key 1-Key 10 and flag fields including Flag 1-Flag 10.

[0029] Finally, a general information table contains all informationregarding the package configuration information. A GenInfoID fieldcontains a number that determines the order in which information will besaved in the data file. A Caption field contains a title next to thedata entry field and identifies which piece of information should beentered in the appropriate area. A Desc field contains comments to theuser by using a mouse-over on the particular line item (Tool Tip) as tothe meaning of each caption or issues related to the caption. A Defaultfield contains an initial value of the data field. Numeric data aregiven an initial value of 0, while text data are initially set to TBD(to be determined). A Section field includes a title of the tab in thegeneral information section of the program. The caption and data entryfield are located on the particular tab based on the value of the field.An Object field describes the nature of the data field. If simple textis to be entered, then the field is given a value of text. If a combobox is to be used to select the data to be entered, the field is giventhe value of combo. A FormUsed field identifies which main page orreport, if any, the data entered into the field is to be displayed on.Finally, a MetricScore field contains a score attached to selectableinformation identifying the importance of the data. As noted above, agreater score is reported for items that are deemed more essential tothe OTR process. Non-essential items are given a score of 0. The overallmetric adds up the scores of all sections which have been left blank orto be determined. A higher score means more open issues are present atthe time of the HOM.

[0030] In the exemplary embodiment of the present invention, theperformance program contains certain data elements that the applicationstores and utilizes in the project information and the configurationsections. A sales department completes the remainder of the projectinformation and configuration to the best of their ability. Applicationsreviews the configuration and project information for accuracy and levelof completion and is responsible for completing the budgetary analysis.Project management maintains the project information and configurationthrough the project execution phase, and engineering maintains thefeatures and options lists and utilizes the program to identify scopechanges.

[0031] The system and process of the present invention will be describedwith reference to the flow charts of FIGS. 2-7 as well as the screenshots of FIGS. 8 and 9. With particular reference to FIG. 2, the programis first loaded in step S1, and the system determines whether the useris creating a new configuration (step S2). If so (YES in step S2), theuser is prompted to select an engine based on the customer providedspecifications (step S3). Once selected, the program reads the defaultmodel configuration table for the selected engine (step S4). Using arecursive function, the application identifies the structure of theoptions. In other words, the application identifies what options aredependent on or nested under higher level options and creates a treeviewgraphical user interface (GUI). A screen shot with the configurationtable and selectable options is shown in FIG. 8.

[0032] Prior to creating and/or modifying a configuration (step S6), thesystem queries whether the user would like to view sales tools in stepS5. If so (YES in step S5), the system carries out the process shown inthe flow diagram of FIG. 7, which will be described in detail below.

[0033] As the user selects options applicable to the project in step S6,the application automatically identifies and deselects all conflictinginformation. Additionally, the system identifies what options have beenselected and locates the associated Boolean operator (found in theBoolean table). The appropriate Boolean operator is then set to true.Conversely, the application also identifies what options have beendeselected and sets those indices to false. These Boolean operators arelater utilized to analyze the budget and features and options lists fordata reports. Additionally, the system identifies the treeview structureand displays applicable options in the treeview based on the user'sselected options and closes all nest levels that are no longeravailable.

[0034] The project information is entered in step S7, and when complete,the system queries whether the project is to be released to engineering(step S8). If not (NO in step S8), a “PTC” file is stored in a harddrive or other data storage device (step S9). If the project is forrelease to engineering (YES in step S8), the system initiates theapproval process (step S10) and subsequently determines whether the userhas received all required approvals (step S11). If so (YES in step S11),a standard folder structure is created in step S12, and theconfiguration is published to the folder structure in step S13. If thenecessary approvals have not been received (NO in step S11), the processreturns to step S6 for further data entry or revision of projectinformation.

[0035] The approval process (step S10) will be further described withreference to FIG. 10. In step S101, a project manager submits theproject for approval. An e-mail notification is sent to an approvalmanager requesting review of the project (step S102). If the approvalmanager has not reviewed the project (NO in step S103), the systemdetermines whether forty-eight (48) hours has passed since the approvalmanager received the e-mail notification (step S104). If not, the systemallows additional time to pass for manager approval. If so (YES in stepS104), the system determines whether seven (7) days have passed sincethe approval manager received the initial e-mail (step S105), and ifnot, the e-mail notification is resent (step S102). In step S106, thesystem determines whether the project has been approved (step S106) andwhether additional approval managers are required to review the project(step S107) If no further approval managers are required to review theproject (NO in step S107), an e-mail notification is sent in step S108to the project manager who submitted the project indicating projectapproval.

[0036] If the project is not approved (NO in step S106), the project isthus rejected (step S109), and an e-mail notification is sent to theproject manager who submitted the project of the project's rejection(step S110).

[0037] The user has the ability to save the project configuration,notes, general information, budgetary analysis, SOS line items, featuresand options list, and all open items based on what information the userhas selected/entered with a metric score associated with each open item.The user can choose between publishing the data to a business server orsaving locally to the computer hard drive. Publishing a file signifiesan official release to the business for review/approval. Each time apackage is published, a separate line item is created in the standardfolder structure on a hidden server. This gives the application theability to track changes and analyze those changes for business impactand statistical analysis. The PIC file stores the package informationlocally without releasing it to the business.

[0038] If the user is not creating a new configuration (NO in step S2),the system queries whether the user is working with an existingpublished project in step S14, and if so (YES in step S14), thepublished file is loaded in step S15. If not (NO in step S14), the PICfile is loaded in step S16.

[0039] Like step S5, the system queries whether the user would like toview sales tools in step S17, and if not (NO in step S17), the systemqueries whether the user is revising the configuration and/or projectinformation in step S18. If so (YES in step S18), the system proceeds tostep S6. If not (NO in step S18), the system proceeds to the processflow illustrated in FIG. 3.

[0040] With reference to FIG. 3, in step S19, the system queries whetherthe user would like to view information concerning the projectconfiguration. If so (YES in step S19), the user is provided options toview PDS (S20), budget (S21), features and options (S22), budgetaryanalysis (S23), or SOS (S24). Selection and viewing of the respectivereports may be limited by the user's permissions. A screen shotillustrating an exemplary report is shown in FIG. 9. In these displays,information is never manipulated or added, which forces the user toenter any necessary change in the configuration or project informationsections.

[0041] In the PDS information view (step S20), the applicationreferences the information found in the general information table. Ifthe information is defined to be available with the user selected report(the PDS in this case), the user input corresponding with the field isincluded in the report. The configuration selected by the user is thendisplayed in the report. Any applicable notes are also presented. Notesare used to identify and describe any non-standard information regardingthe customer specific package. In other words, any customer requestsoutside the typical scope of supplies.

[0042] In the budget information view (step S21), the applicationreferences the information found in the general information table. Ifthe information is defined to be available with the user selected report(the budget in this case), the user input corresponding with the fieldis included in the report. The application references the informationfound in the budget table. Each line item in the table is analyzedagainst the Boolean values (i.e., the configuration). If the keys andflags match the Boolean values found in the configuration, then the lineitem is added to the report. All notes and their associated costs arethen displayed in a special request section. Each budgetary line itemhas specific customer options associated with it. These options areoften complex, for instance: if given five options a, b, c, d and e, thebudgetary line item may require (1) the user to select option a, c andd, (2) the user not to select b, and (3) not be affected one way or theother by e. In this case, the database would show the key associatedwith option a (found in the package options table) with a TRUE flagfield.

[0043] In the features and options list (step S22), the applicationreferences the information found in the features and options table. Ifthe information is defined to be available with the user selectedreport, the user input corresponding with the field is included in thereport. The application references the information found in the featuresand options table. Each line item in the table is analyzed against theBoolean values (i.e., the configuration). If the keys and flags matchthe Boolean values found in the configuration, then the line item isadded to the report.

[0044] In the budgetary analysis view (step S23), the applicationcreates a budget and pulls the line items into the budgetary analysisformat. Text boxes are supplied for the user to input actual cost perline item. The application then calculates variance between thepackage's actual cost and initial estimated cost.

[0045] In the SOS information view (step S24), the applicationreferences the information found in the general information table. Ifthe information is defined to be available with the user selectedreport, the user input corresponding with the field is included in thereport. The application then reviews all of the packages associated tothe current project and reports all SOS line items.

[0046] If the user does not desire to view information (NO in step S19),the user is provided with options to modify the drawing list (step S25),create and/or modify the budgetary analysis (step S26), or maintain thetool (step S27). The selected processes in steps S25, S26 and S27 areshown in the flow charts of FIGS. 4, 5 and 6, respectively.

[0047] If the user intends to modify the drawing list (YES in step S25),with reference to FIG. 4, the system selects the features and optionslist option (step S251) and subsequently selects a modify option (stepS252). The system then queries whether the user intends to add a drawingor part (step S253), delete a drawing or part (step S254) or return tothe configuration (NO in step S254). In either instance (YES in eitherstep S253 or step S254), the add option is selected (step S255) and themodification is entered (step S256). Various levels of approval may berequired for such modifications, and the system determines whether anyrequired approval has been received in step S257. If not (NO in stepS257), the system returns to step S256 for further modification. If so(YES in step S257), the modified configuration is published to thefolder structure in step S258.

[0048] With reference to FIG. 5, if the user desires to create and/ormodify the budgetary analysis (YES in step S26), the system selects thebudgetary analysis option in step S261, selects the modify option instep S262, and enables the user to enter the modification in step S263.The system queries whether the user has received any required approvalin step S264, and if so (YES in step S264), the modification ispublished to the folder structure in step S265. If any required approvalhas not been received (NO in step S264), the system returns to step S263for further modification entry.

[0049] If the user desires to maintain the tool (YES in step S27), withreference to FIG. 6, the system performs tool maintenance in step S271and subsequently returns the process to the configuration section. Inthe maintenance process, the database can be modified or manipulated inany fashion. Due to the structure of the application, the results willrange from modifying reports to adding package options or even an entirepackage.

[0050] With respect to effecting changes in the configuration, fieldsare supplied to allow the user to create a document used to trackcontractual or scope changes defined through the life of the project.This view also allows the user to load previous change orders that applyto the loaded package.

[0051] The process flow for viewing sales tools will be described withreference to FIG. 7. In this process, the user is provided with optionsto view brochures (step S28), view technical specifications (step S29),view proposal drawings (step S30), generate a proposal (step S31), orreturn to the configuration (step S32). In the brochure view process(YES in step S28), the user is prompted to select the brochure option(step S281), and the information is displayed (step S282). A similarprocess is carried out with respect to technical specifications (YES instep S29) in steps S291 and S292 and generate proposal (YES in step S31)in steps S311 and S312. Similar to budget and features and options, thetechnical specification is generated dynamically. This documentdescribes the package specific information based on what the user hasselected/inputted.

[0052] In viewing the proposal drawings (YES in step S30), the userselects the drawing option in step S301, a search tool is navigated instep S302, and the information is displayed in step S303. Severaldifferent drawings may be available based on the selected engine/model.The user must select which drawing to view.

[0053] The program is responsible for producing the production datasheet (PDS), the budget, the features and options list (F&O), thebudgetary analysis, and the sales order summary (SOS). In addition, theprogram must have the capability of producing the metric data asdiscussed above. The PDS contains information that is required forengineering to order parts and manufacturing to build the package. Thisinformation includes items such as customer information, siteconditions, testing information, among other information as defined inthe general information table. In addition to the package information,the PDS also contains the entire project scope.

[0054] The budget provides the item costs as defined in the budget costtable and the package information (required items are defined in thegeneral information table). The budget document then sums the item costsinto a section total (again, this information is included in the budgetcost table). The total package cost is then calculated by summing upeach of the section totals. The features and options list is created bylisting each of the drawings, as defined in the features and optionstable, that apply to the identified package configuration. The list isorganized into sections that are also defined in the table. Thebudgetary analysis reads the information from the initial budget, allowsthe user the ability to enter actual costs associated with each lineitem, calculates a variance per line item, allows the user to enter adescription of the variance, and then summarizes the variance. Thesummary separates the line items into one of two categories. The basepackaging is defined as necessary items for a GTG package. These itemsare identified in the budget cost table. The remaining items arecategorized as standard options.

[0055] Generally, the program is designed to have the functionality ofmaintaining project information and configuration from the ITO processto the project completion. Furthermore, the program formats thisinformation appropriately to provide the business with the requireddocumentation and information. Specifically, as noted above, the programis required to create the budget, PDS, F&O (including productionreleases, customer transmittals, and required dates), the SOS and abudgetary analysis document. In addition to the listed functions, theprogram tracks the project using the ITO metrics on quality. The metricsinclude open items, specific revisions that were made, the personnelthat made the revisions, when the revisions were made, and why.

[0056] The system of the present invention provides the ability toautomate, direct and monitor a project development through businessprocesses. The system effects streamlined project documentation,comprehensive single source data entry and stores historical data whilemaintaining current and up-to-date information, including projectinformation and documentation, package availability and options,budgetary information, base offerings, and features and options lists.Through direct electronic routing, automated approval processes formodifications and/or base configurations can be obtained. A runningproject budget can be maintained enabling budgetary analysiscapabilities. The system maintains and generates reports on change orderdescriptions, magnitude of change calculations, metric data, open items,administration capabilities and project information location/structure.The system enables automatic updating for the database as well as forexecutable operations. Still further, the system accommodates multiplepoints of data entry and processes data using standard document formats.

[0057] While the invention has been described in connection with what ispresently considered to be the most practical and preferred embodiments,it is to be understood that the invention is not to be limited to thedisclosed embodiments, but on the contrary, is intended to cover variousmodifications and equivalent arrangements included within the spirit andscope of the appended claims.

What is claimed is:
 1. A method of processing project data comprising:(a) receiving customer specifications; (b) identifying an engine modelbased on the customer specifications; (c) storing package options basedon the engine model identified in (b); (d) enabling a user to select thepackage options from the stored package options; and (e) generatingselected reports based on the package options selected in (d).
 2. Amethod according to claim 1, wherein step (e) is practiced by generatinga budget report based on the package options selected in (d).
 3. Amethod according to claim 2, wherein step (e) is further practiced bystoring line item cost estimates for each component in the engine modeland enabling a comparison with actual costs.
 4. A method according toclaim 1, wherein step (c) is practiced by storing package options with anesting structure.
 5. A method according to claim 1, wherein step (e) ispracticed by generating a features and options report based on thepackage options selected in (d), the features and options reportincluding a list of figures available based on the engine model and theselected package options.
 6. A method according to claim 1, wherein step(e) is practiced by generating a sales order summary report based on thepackage options selected in (d), the sales order summary reportincluding a summary of all equipment sold.
 7. A method according toclaim 1, wherein step (d) comprises enabling the user to update/modifythe selected package options, and storing historical project dataidentifying updated/modified information including a particular user,date and time of update/modification.
 8. A method according to claim 1,wherein step (d) comprises storing the selected package options locallyor publishing the selected package options for global use.
 9. A methodaccording to claim 1, wherein step (e) comprises enabling at least oneapproval manager to review items requiring approval.
 10. A methodaccording to claim 9, wherein if multiple approvals are required for oneor more items, the method comprising automatically successively routinga report including the items requiring approval to each approvalmanager.
 11. A system for processing project data, the systemcomprising: means for receiving customer specifications; means foridentifying an engine model based on the customer specifications; meansfor storing package options based on the identified; means for enablinga user to select the package options from the stored package options;and means for generating selected reports based on the selected packageoptions.
 12. A system for processing project data, the systemcomprising: a user interface for receiving customer specifications andidentifying an engine model based on the customer specifications; and aprocessor including a memory storing package options that are segregatedbased on the identified engine model, the processor enabling a user toselect the package options from the stored package options via the userinterface, wherein the processor generates selected reports based on theselected package options.